home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-10-17 | 1.9 KB | 37 lines | [TEXT/GEOL] |
- Item 0431105 17-Oct-89 01:26
-
- From: UK0016 Icon Technology UK
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: Eiffel, C++ & MacApp
-
- At the recent European Developers Conference in Paris I gave a talk entitled
- "MacApp: The Key to Quality" in which I tried to paraphrase some of Bertrand
- Meyer's justification of OOP. In it I stressed that MacApp was a vital
- component of an OOPS based on Object Pascal. I agree with Kurt Schmucker that
- if a new language arrives boasting objects, then it is of little use unless it
- supports the MacApp classes. On the other hand there is a risk of stagnation if
- MacApp is seen as some de facto standard. In my talk I concluded by saying that
- Object Pascal & MacApp should be seen as a beginning to the new tradition of
- Object Oriented Design and Development. They should not be seen as the end.
-
- Eiffel & C++ (and any other contenders) must, in the short term, support MacApp
- to stand any chance of gaining acceptance (this is simple economics). On the
- other hand, the additional OOP features such as Genericity and Multiple
- Inheritance must surely end up being exploited by MacApp (evolution and not
- revolution).
-
- Eiffel is a much smaller, cleaner and well thought out language than C++. It
- also comes with some nifty tools and a good class library. The argument that
- anything that can be done in language A can be simulated by macros in lower
- level language B is facile, and certainly not any reason for rejecting A (we'd
- still all be writing in Assembler if this were true). I can, on the other hand,
- appreciate that anyone who has devoted much time and effort (= money) to
- learning C will be attracted to C++. I simply don't have that problem, and so I
- hope I can make a much more objective choice (actually I don't have that choice
- yet, because there isn't a Mac version of Eiffel!).
-
- Regards, Keith Lander
-
-